Skip to content

Conversation

@golharam
Copy link
Contributor

@golharam golharam commented Sep 20, 2025

The files API acts as a metadata catalog that:

Stores file metadata (filename, path, size, type, etc.) in the database
Supports multiple storage backends (local, S3, Azure, GCS) via the StorageBackend enum
Uses file_path field to store the actual location (S3 URI, local path, etc.)

Key Benefits of Database Registration

Fast querying: Filter by entity, type, date without scanning S3
Metadata enrichment: Add descriptions, tags, relationships
Access control: Track permissions and public/private status
Integration: Link files to projects/runs

Existing S3 files remain in place
Gain all the API benefits (search, filtering, metadata)
One-time setup process
Future files can be registered as they're created

Ryan Golhar and others added 2 commits September 26, 2025 21:49
@golharam golharam marked this pull request as ready for review September 27, 2025 01:52
@golharam golharam requested a review from EricSDavis September 27, 2025 01:52
@golharam golharam mentioned this pull request Sep 27, 2025
4 tasks
@golharam golharam removed the request for review from EricSDavis October 7, 2025 14:28
@golharam golharam marked this pull request as draft October 7, 2025 14:28
@golharam
Copy link
Contributor Author

golharam commented Oct 7, 2025

This branch has code I'm not yet ready to get rid of, so keeping this branch alive and unmerged.

@golharam golharam added help wanted Extra attention is needed post-phase-1 and removed help wanted Extra attention is needed labels Oct 7, 2025
@golharam golharam changed the title Files api DB Files Support Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants